Post

Replies

Boosts

Views

Activity

Reply to Diagnosing MetricKit crash reports with EXC_CRASH / SIGKILL with no termination reason
If you mean that MetricKit on iOS 27 is better about including terminationReason, I'll watch for that. I do also plan to support the new MetricKit. As for the Xcode organizer, its top entry in Crashes under Reports does look like a 0xdead10cc termination - it carries that code if I go look at the raw report on disk (side note - the Organizer does not expose these terminations well - FB12292887). But on the Terminations screen under Metrics, it shows background terminations as being 98% System Pressure, and 1% File Lock and 1% Other. I don't believe 1% of terminations works out to enough to explain the numbers of reports I've been seeing, and certainly not to the count shown on that top entry in Crashes under Reports. As another signal, the original impetus for me chasing this is that the Crashes metric in App Store Connect for my app shows a higher crash count per day than I expect, not matching any other reporting source I have. It's why I started uploading all my MetricKit reports from devices in the field.
Topic: App & System Services SubTopic: Core OS Tags:
Sep ’26
Reply to What determines the size of a UIScrollEdgeElementContainerInteraction with a hard edge effect?
The behavior has changed (and I’d say regressed) with iOS 27 seed one. As of iOS 26.5, if the view with the scroll edge effect contains a UIVisualEffectView with a glass effect, the blur extends down to the bottom edge of the view. On iOS 27.0 seed one, the effect only goes to the bottom edge of the effect view. I've attached a new sample app and screen recordings to the feedback mentioned above.
Topic: UI Frameworks SubTopic: UIKit Tags:
Jun ’26
Reply to Symbolicating Crash Reports for Mac Catalyst App
I'm seeing the same issue with Xcode 16.1 on macOS Sequoia 15.1 when building my Catalyst app. I found this StackOverflow comment saying if you change the Debug Information Format build setting away from and back to its default, "DWARF with dSYM file", the setting value becomes explicit in the project file and Xcode is forced to generate the dSYM for the main app target. This seems to work for me.
Oct ’24
Reply to Unable to Disable/Hide Writing Tools in iOS 18
I was able to work around this issue with NSInvocation in Objective-C: WKWebViewConfiguration *config = [[WKWebViewConfiguration alloc] init]; SEL selector = @selector(setWritingToolsBehavior:); NSMethodSignature *sig = [config methodSignatureForSelector:selector]; NSInvocation *invocation = [NSInvocation invocationWithMethodSignature:sig]; [invocation setSelector:selector]; [invocation setTarget:config]; NSInteger arg = (NSInteger)UIWritingToolsBehaviorNone; [invocation setArgument:&arg atIndex:2]; [invocation invoke]; This works to set the writingToolsBehavior to none, and I don't get the Writing Tools option in my popup when selecting text in my WKWebView.
Topic: Safari & Web SubTopic: General Tags:
Oct ’24
Reply to Diagnosing MetricKit crash reports with EXC_CRASH / SIGKILL with no termination reason
If you mean that MetricKit on iOS 27 is better about including terminationReason, I'll watch for that. I do also plan to support the new MetricKit. As for the Xcode organizer, its top entry in Crashes under Reports does look like a 0xdead10cc termination - it carries that code if I go look at the raw report on disk (side note - the Organizer does not expose these terminations well - FB12292887). But on the Terminations screen under Metrics, it shows background terminations as being 98% System Pressure, and 1% File Lock and 1% Other. I don't believe 1% of terminations works out to enough to explain the numbers of reports I've been seeing, and certainly not to the count shown on that top entry in Crashes under Reports. As another signal, the original impetus for me chasing this is that the Crashes metric in App Store Connect for my app shows a higher crash count per day than I expect, not matching any other reporting source I have. It's why I started uploading all my MetricKit reports from devices in the field.
Topic: App & System Services SubTopic: Core OS Tags:
Replies
Boosts
Views
Activity
Sep ’26
Reply to What determines the size of a UIScrollEdgeElementContainerInteraction with a hard edge effect?
The behavior has changed (and I’d say regressed) with iOS 27 seed one. As of iOS 26.5, if the view with the scroll edge effect contains a UIVisualEffectView with a glass effect, the blur extends down to the bottom edge of the view. On iOS 27.0 seed one, the effect only goes to the bottom edge of the effect view. I've attached a new sample app and screen recordings to the feedback mentioned above.
Topic: UI Frameworks SubTopic: UIKit Tags:
Replies
Boosts
Views
Activity
Jun ’26
Reply to Symbolicating Crash Reports for Mac Catalyst App
I'm seeing the same issue with Xcode 16.1 on macOS Sequoia 15.1 when building my Catalyst app. I found this StackOverflow comment saying if you change the Debug Information Format build setting away from and back to its default, "DWARF with dSYM file", the setting value becomes explicit in the project file and Xcode is forced to generate the dSYM for the main app target. This seems to work for me.
Replies
Boosts
Views
Activity
Oct ’24
Reply to Unable to Disable/Hide Writing Tools in iOS 18
I was able to work around this issue with NSInvocation in Objective-C: WKWebViewConfiguration *config = [[WKWebViewConfiguration alloc] init]; SEL selector = @selector(setWritingToolsBehavior:); NSMethodSignature *sig = [config methodSignatureForSelector:selector]; NSInvocation *invocation = [NSInvocation invocationWithMethodSignature:sig]; [invocation setSelector:selector]; [invocation setTarget:config]; NSInteger arg = (NSInteger)UIWritingToolsBehaviorNone; [invocation setArgument:&arg atIndex:2]; [invocation invoke]; This works to set the writingToolsBehavior to none, and I don't get the Writing Tools option in my popup when selecting text in my WKWebView.
Topic: Safari & Web SubTopic: General Tags:
Replies
Boosts
Views
Activity
Oct ’24